| Summary: | cp failures during PublishArtifacts should cause the step to fail | ||
|---|---|---|---|
| Product: | [Infrastructure] AutoBuilder | Reporter: | Joshua Lock <joshuagloe> |
| Component: | autobuilder | Assignee: | Mariano Lopez <mariano.lopez> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | High | CC: | anibal.limon, infras.ab.watcher, Infras.watcher, leonardo.sandoval.gonzalez, mariano.lopez, pidge |
| Version: | 2.2 | ||
| Target Milestone: | 2.2 M4 | ||
| Hardware: | x86 | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | No (bug/feature does not impact docs) | |
|
Description
Joshua Lock
2016-09-22 08:13:13 UTC
It seems the problem is within PublishArtifacts.py, and it seems it will be very difficult to change the way it runs the command in the worker, because it will iterate over the artifacts and will build a huge command and execute it with just one call in the worker. I added a pipeline in the cp commands of PublishArtifacts.py, with these it will set an env var that later will be checked to mark the exit as successful of failed. I tested locally and it works fine, I'll test in GDC autobuilders before submitting the patch. The test on the GDC autobuilders was successful. Sent patch to the mailing list: https://lists.yoctoproject.org/pipermail/yocto/2016-September/032183.html This change has been merged to the yocto-autobuilder and deployed to the build cluster. |