Testing bot PR263 by building and uploading CaDiCaL #73
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Instance
|
|
bot: build repo:swl-deb10 arch:zen2 |
Updates by the bot instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
4 tasks
|
All 4 builds jobs launched via (#73 (comment)) have finished. Job The bot's configuration when processing the bucket_name = {
"nessi-2022.11-swl-deb10": "dev-pr254-3",
"nessi-2023.06-swl-deb10": "dev-pr254-2",
"nessi-2023.06-swl-deb11": "dev-pr254"}
upload_policy = latest
metadata_prefix = {
"nessi-2022.11-swl-deb10": "new11-10/'${github_repository}'/'${pull_request_number}'",
"nessi-2023.06-swl-deb10": "new06-10/'${github_repository}'/'${pull_request_number}'",
"nessi-2023.06-swl-deb11": "new06-11/'${github_repository}'/'${pull_request_number}'"}
tarball_prefix = {
"nessi-2022.11-swl-deb10": "tb22.11/'${github_repository}'/'${pull_request_number}'",
"nessi-2023.06-swl-deb10": "tb23.06-deb10/'${github_repository}'/'${pull_request_number}'",
"nessi-2023.06-swl-deb11": "tb23.06-deb11/'${github_repository}'/'${pull_request_number}'"} |
|
None of the successful jobs was accurately identified as |
|
Added a bit more logging output. |
trz42
added
bot:deploy
|
The string values seem ok. Changed the comparison operator too. diff --git a/tasks/deploy.py b/tasks/deploy.py
index 7855416..7092545 100644
--- a/tasks/deploy.py
+++ b/tasks/deploy.py
@@ -189,7 +189,9 @@ def check_job_status(job_dir):
log(f"{fn}(): no result file '{job_result_file_path}' or reading it failed\n")
return False
- if job_status is job_metadata.JOB_RESULT_SUCCESS:
+ log(f"{fn}(): job status is {job_status} (compare against {job_metadata.JOB_RESULT_SUCCESS})\n")
+
+ if job_status == job_metadata.JOB_RESULT_SUCCESS:
# case (2): result file && status = SUCCESS --> return True
log(f"{fn}(): found status 'SUCCESS' from '{job_result_file_path}'\n")
return True |
trz42
added
bot:deploy
|
Rerun builds after updates to bot PR (also removed unused settings in bot: build repo:swl-deb10 arch:zen2 |
Updates by the bot instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
Same build result as before. Re-setting |
trz42
added
bot:deploy
|
Some config settings weren't updated which lead to the error |
trz42
added
bot:deploy
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR to test new deploy code relying on result files ... see EESSI/eessi-bot-software-layer#263
Software to be installed:
Test scenarios:
bot:deploylabel and check what gets uploaded and where (which S3 buckets). Documentupload_policy,_prefixsettings for upload directories, bucket specs, ...