-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
.github/workflows: use write-artifacts and prevent rebuild #40
Conversation
Will need to fix the option in Testground, it looks like we got a frankenfile: half input, half output. ...
[groups.build_config.build_args]
CARGO_FEATURES = "libp2pv0470"
[groups.build]
[groups.run]
artifact = "73b08cb20924"
tTarget }}
target = "{{ $.Env.GitTarget }}"
{{ end }}
[groups.build_config]
path = "./go/"
build_base_image = 'golang:{{ .GoVersion }}-buster'
modfile = "{{ .Modfile }}"
[groups.build_config.dockerfile_extensions]
# deal with dependency changes in master until we create the new vx.y.z instance
pre_build = """
RUN cd ${PLAN_DIR} && \
go mod download github.com/libp2p/go-libp2p && \
go mod tidy -compat={{ .GoVersion }}
"""
{{ end }}
{{ end }}
{{ end }}
{{ end }}
{{ with (load_resource "./rust.toml") }}
{{ with (index .groups 0) }}
... |
28eadfc
to
0da4550
Compare
I just experience another docker pull error during the install:
adding back the retry during install. I also bumped the build timeout because it creates noise in the long tests. Bear with me, we'll eventually drop this. |
081d449
to
d523e5c
Compare
@mxinden @marten-seemann @galargh I'm for the week but feel free to merge (it fixes #39)
|
What does Where are these artifacts saved? How large do we expect them to be? Where are they stored between builds? |
From https://docs.testground.ai/running-test-plans#building-a-composition and https://docs.testground.ai/concepts-and-architecture/builders#examples I gather that
If I understand the documentation correctly, we wouldn't be creating any new artifacts but only modifying the provided composition file.
I think it should be comparable to the input composition file so I don't think we need to worry about the size.
test-plans/.github/workflows/run-composition.yml Lines 96 to 103 in d523e5c
Laurent added the composition file to the build bundle artifact here. |
|
||
for i in 1 2 3; do | ||
echo "=== Attempt $i ===" | ||
/bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/testground/testground/master/install.sh)" && \ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Now that there are retries we could download the shell script ahead of the loop.
2022-09-16 libp2p triage conversation: @libp2p/ipdx feel free to merge. You're trusted on what's right to do here. |
I saw some other PR mentioning |
d523e5c
to
3b4a8b1
Compare
Thanks team, I just rebased over master, will merge soon, A few answers:
Ignore testground build --file my-composition.toml --output composition-after-build-that-contains-build-outcomes.toml
testground run --file composition-after-build-that-contains-build-outcomes.toml Right now, this feature exists behind the (I'm not happy with the name and implementation either, we'll deprecate/break this flag later). |
fixes #39
Use the
write-artifacts
option during the build.With this option, Testground replaces the composition file with the one produced by the build step (template generation applied, build artifact set).
With this we:
Tasks
write-artifacts
to correctly truncate & close the output testground/testground#1444