action #20788
closed
- Related to action #23428: failed job does not show HDD in assets even if it was uploaded. added
- Priority changed from Normal to Low
- Target version set to future
to be clear: the upload does not fail, but associating the job with the 'new' asset fails due to a DB constraint. But I claim this situation is a corner case, as overwriting assets makes reproducible tests a nightmare.
And from what I remember, the setting was more an oversight than a concrete user story
- Target version changed from future to future
- Status changed from New to Feedback
- Assignee set to okurz
- Status changed from Feedback to Resolved
merged. I don't think it's worth to check in production.
Also available in: Atom
PDF