platformio / platformio/platformio-core

pio remote run -t nobuild -t upload not working

Open
#3,302 3 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted remote
Dominant language
Python
Stars
9.5k
Forks
905
Avg merge
2d 13h
Merged PRs (30d)
2

Description

-t nobuild not working on a remote run but works fine on a local run

Operating system: Tested on Windows 10, Ubuntu and Gitpod cloud

PlatformIO Version (platformio --version):

PlatformIO, version 4.1.0

Description of problem

"pio remote run -t nobuild -t upload" not working but
"pio run -t nobuild -t upload" works fine

Community post related to the issue at

https://community.platformio.org/t/upload-latest-build-without-a-compile-link/9520/9


Configuration

Normal UNO Arduino setup
Serial proof of upload

Steps to Reproduce
  1. So running VS-Code local on a windows machine with

pio account login
pio remote agent start

  1. Then on a ubuntu laptop running VS-Code upload the original sketch

pio account login
pio remote run -t upload

  1. Now change your code to "version 2!" and save the file. Then try to upload the old compiled verison 1.

pio remote run -t nobuild -t upload

Actual Results

Version 2!

Expected Results

Version 1!

If problems with PlatformIO Build System:

The content of platformio.ini:


[env:uno]
platform = atmelavr
board = uno
framework = arduino

Source file to reproduce issue:


#include <Arduino.h>

void setup() {
	Serial.begin(9600);
}

void loop() {
	Serial.println("Version 1! ");
	delay(1000);
}

Additional info

Being able to use "-t nobuild" can be very useful when you just want to install a pre-tested working program for that board. I can give my students the pre-tested program and not worry if they have made any environment changes that effect the build.

I found this bug when testing with a cloud method using gitpod.io but the bug seems to happen even when using VS Code on 2 local machines.

Gitpod Cloud docker github of it my-gitpod-of-openthread
Open in Gitpod

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the difference between pio run -t nobuild -t upload and pio remote run -t nobuild -t upload with the provided platformio.ini and Arduino sketch. Compare the remote upload behavior after changing the sketch; done means the remote command uploads the previously built Version 1 rather than rebuilding Version 2.

Written by the indexing model from the issue text.

Assessment

Tech stack
arduino, python
Domain
build-system, cli
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.